Skip to content

Conversation

camilamacedo86
Copy link
Contributor

@camilamacedo86 camilamacedo86 commented Aug 8, 2025

This commit migrates the OLMv1 single and own namespace watch mode tests from openshift/origin/test/extended/olm/olmv1-singleownnamespace.go to this repository. This is part of the effort to move component-specific tests into their respective downstream locations.

PS.: See that we need to name the tests to add [Serial]

Tests

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fa4a1a60-7dad-11f0-856b-9bcfe9c1c15c-0

@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 8, 2025

@camilamacedo86: This pull request references OPRUN-4057 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set.

In response to this:

This commit migrates the OLMv1 single and own namespace watch mode tests from openshift/origin/test/extended/olm/olmv1-singleownnamespace.go to this repository. This is part of the effort to move component-specific tests into their respective downstream locations.

Assisted-by: Gemini

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Aug 8, 2025
@openshift-ci openshift-ci bot requested review from bentito and thetechnick August 8, 2025 21:52
@camilamacedo86 camilamacedo86 changed the title OPRUN-4057: Migrate single/own namespace tests WIP: OPRUN-4057: Migrate single/own namespace tests Aug 8, 2025
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 8, 2025
@camilamacedo86 camilamacedo86 force-pushed the single-add-ote branch 2 times, most recently from fc79ef4 to 0b054e2 Compare August 8, 2025 22:43
@@ -1,4 +1,34 @@
[
{
"name": "[sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected] OLMv1 operator installation support for singleNamespace watch mode with quay-operator should install a cluster extension successfully",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

@camilamacedo86 camilamacedo86 Aug 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should add SERIAL in the names, but they are not today
We properly renamed the test tracking both over the time

"environmentSelector": {}
},
{
"name": "[sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected] OLMv1 operator installation support for ownNamespace watch mode with quay-operator should install a cluster extension successfully",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

@camilamacedo86 camilamacedo86 Aug 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should add SERIAL in the names, but they are not today
We properly renamed the test tracking both over the time

"environmentSelector": {}
},
{
"name": "[sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected] OLMv1 operator installation support for ownNamespace watch mode with an operator that does not support ownNamespace installation mode should fail to install a cluster extension successfully",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

@camilamacedo86 camilamacedo86 Aug 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should add SERIAL in the names, but they are not today
We properly renamed the test tracking both over the time

@camilamacedo86 camilamacedo86 force-pushed the single-add-ote branch 2 times, most recently from c51fde3 to 4c028b6 Compare August 11, 2025 10:45
@camilamacedo86 camilamacedo86 changed the title WIP: OPRUN-4057: Migrate single/own namespace tests OPRUN-4057: Migrate single/own namespace tests Aug 11, 2025
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 11, 2025
@@ -1,4 +1,34 @@
[
{
"name": "[sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected][Serial] OLMv1 operator installation support for singleNamespace watch mode with quay-operator should install a cluster extension successfully",
Copy link
Contributor Author

@camilamacedo86 camilamacedo86 Aug 11, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should add SERIAL in the names, but they are not today
We properly renamed the test tracking both over the time

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 11, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 11, 2025

@camilamacedo86: This pull request references OPRUN-4057 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set.

In response to this:

This commit migrates the OLMv1 single and own namespace watch mode tests from openshift/origin/test/extended/olm/olmv1-singleownnamespace.go to this repository. This is part of the effort to move component-specific tests into their respective downstream locations.

Local Tests

$ ./bin/olmv1-tests-ext run-suite olmv1/all
 [INFO] [env] Using kubeconfig: /Users/camilam/.kube/cluster-bot.kubeconfig[INFO] [env] Cluster environment initialized (OpenShift: true)  Running Suite:  - /Users/camilam/go/src/github/operator-framework-operator-controller/openshift/tests-extension
 ===============================================================================================================
 Random Seed: 1754910630 - will randomize all specs

 Will run 1 of 1 specs
 ------------------------------
 [sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected][Serial] OLMv1 operator installation support for singleNamespace watch mode with quay-operator should install a cluster extension successfully
 /Users/camilam/go/src/github/operator-framework-operator-controller/openshift/tests-extension/test/olmv1-singleownnamespace.go:57
   STEP: checking if OpenShift is available for tests @ 08/11/25 12:10:31.234
   STEP: ensuring no ClusterExtension and CRD for quay-operator @ 08/11/25 12:10:31.235
   STEP: creating namespace olmv1-quay-singlens-ns-dvnh for single-namespace tests @ 08/11/25 12:10:31.803
   STEP: creating ServiceAccount @ 08/11/25 12:10:31.925
   STEP: ensuring ServiceAccount is available before proceeding @ 08/11/25 12:10:32.049
   STEP: registering cleanup for ServiceAccount @ 08/11/25 12:10:32.168
   STEP: creating ClusterRoleBinding @ 08/11/25 12:10:32.168
   STEP: ensuring ClusterRoleBinding is available before proceeding @ 08/11/25 12:10:32.289
   STEP: registering cleanup for ClusterRoleBinding @ 08/11/25 12:10:32.411
   STEP: creating ClusterExtension with the watch-namespace annotation @ 08/11/25 12:10:32.412
   STEP: registering cleanup for ClusterExtension @ 08/11/25 12:10:32.572
   STEP: waiting for the ClusterExtension to be installed @ 08/11/25 12:10:32.573
   STEP: cleanup: deleting ClusterExtension install-quay-singlens-ce-x8gb @ 08/11/25 12:10:34.935
   STEP: cleanup: deleting ClusterRoleBinding install-quay-singlens-crb-x8gb @ 08/11/25 12:10:34.936
   STEP: cleanup: deleting ServiceAccount install-quay-singlens-sa-x8gb in namespace olmv1-quay-singlens-ns-dvnh @ 08/11/25 12:10:34.936
   STEP: cleaning up namespace olmv1-quay-singlens-ns-dvnh @ 08/11/25 12:10:34.936
 • [3.932 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 3.932 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
 Running Suite:  - /Users/camilam/go/src/github/operator-framework-operator-controller/openshift/tests-extension
 ===============================================================================================================
 Random Seed: 1754910630 - will randomize all specs

 Will run 1 of 1 specs
 ------------------------------
 [sig-olmv1][OCPFeatureGate:NewOLM] OLMv1 CRDs should be installed
 /Users/camilam/go/src/github/operator-framework-operator-controller/openshift/tests-extension/test/olmv1.go:39
   STEP: verifying CRD clusterextensions.olm.operatorframework.io @ 08/11/25 12:10:35.291
   STEP: verifying CRD clustercatalogs.olm.operatorframework.io @ 08/11/25 12:10:35.421
 • [0.381 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 0.381 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
 Running Suite:  - /Users/camilam/go/src/github/operator-framework-operator-controller/openshift/tests-extension
 ===============================================================================================================
 Random Seed: 1754910630 - will randomize all specs

 Will run 1 of 1 specs
 ------------------------------
 [sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected][Serial] OLMv1 operator installation support for ownNamespace watch mode with an operator that does not support ownNamespace installation mode should fail to install a cluster extension successfully
 /Users/camilam/go/src/github/operator-framework-operator-controller/openshift/tests-extension/test/olmv1-singleownnamespace.go:211
   STEP: checking if OpenShift is available for tests @ 08/11/25 12:10:35.549
   STEP: ensuring no ClusterExtension and CRD for openshift-pipelines-operator-rh @ 08/11/25 12:10:35.549
   STEP: deleting ClusterExtension install-pipelines-fail-own-ns-ce-d6v4 (package: openshift-pipelines-operator-rh) @ 08/11/25 12:10:35.681
   STEP: creating namespace olmv1-pipelines-fail-own-ns-ns-p6gb for failing tests @ 08/11/25 12:10:36.044
   STEP: creating ServiceAccount @ 08/11/25 12:10:36.167
   STEP: ensuring ServiceAccount is available before proceeding @ 08/11/25 12:10:36.289
   STEP: registering cleanup for ServiceAccount @ 08/11/25 12:10:36.41
   STEP: creating ClusterRoleBinding @ 08/11/25 12:10:36.41
   STEP: ensuring ClusterRoleBinding is available before proceeding @ 08/11/25 12:10:36.534
   STEP: registering cleanup for ClusterRoleBinding @ 08/11/25 12:10:36.96
   STEP: creating ClusterExtension with the watch-namespace annotation @ 08/11/25 12:10:36.961
   STEP: registering cleanup for ClusterExtension @ 08/11/25 12:10:37.11
   STEP: waiting for the ClusterExtension to fail installation @ 08/11/25 12:10:37.111
   STEP: cleanup: deleting ClusterExtension install-pipelines-fail-own-ns-ce-h88d @ 08/11/25 12:10:38.345
   STEP: cleanup: deleting ClusterRoleBinding install-pipelines-fail-own-ns-crb-h88d @ 08/11/25 12:10:38.346
   STEP: cleanup: deleting ServiceAccount install-pipelines-fail-own-ns-sa-h88d in namespace olmv1-pipelines-fail-own-ns-ns-p6gb @ 08/11/25 12:10:38.346
   STEP: cleaning up namespace olmv1-pipelines-fail-own-ns-ns-p6gb @ 08/11/25 12:10:38.346
 • [2.923 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 2.923 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
 Running Suite:  - /Users/camilam/go/src/github/operator-framework-operator-controller/openshift/tests-extension
 ===============================================================================================================
 Random Seed: 1754910630 - will randomize all specs

 Will run 1 of 1 specs
 ------------------------------
 [sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected][Serial] OLMv1 operator installation support for ownNamespace watch mode with quay-operator should install a cluster extension successfully
 /Users/camilam/go/src/github/operator-framework-operator-controller/openshift/tests-extension/test/olmv1-singleownnamespace.go:134
   STEP: checking if OpenShift is available for tests @ 08/11/25 12:10:38.473
   STEP: ensuring no ClusterExtension and CRD for quay-operator @ 08/11/25 12:10:38.473
   STEP: deleting ClusterExtension install-quay-singlens-ce-x8gb (package: quay-operator) @ 08/11/25 12:10:38.648
   STEP: creating namespace olmv1-quay-own-ns-ns-nmnv for own-namespace tests @ 08/11/25 12:10:41.138
   STEP: creating ServiceAccount @ 08/11/25 12:10:41.26
   STEP: ensuring ServiceAccount is available before proceeding @ 08/11/25 12:10:41.379
   STEP: registering cleanup for ServiceAccount @ 08/11/25 12:10:41.497
   STEP: creating ClusterRoleBinding @ 08/11/25 12:10:41.497
   STEP: ensuring ClusterRoleBinding is available before proceeding @ 08/11/25 12:10:41.629
   STEP: registering cleanup for ClusterRoleBinding @ 08/11/25 12:10:41.749
   STEP: creating ClusterExtension with the watch-namespace annotation @ 08/11/25 12:10:41.749
   STEP: registering cleanup for ClusterExtension @ 08/11/25 12:10:41.87
   STEP: waiting for the ClusterExtension to be installed @ 08/11/25 12:10:41.871
   STEP: cleanup: deleting ClusterExtension install-quay-own-ns-ce-bx7w @ 08/11/25 12:10:44.227
   STEP: cleanup: deleting ClusterRoleBinding install-quay-own-ns-crb-bx7w @ 08/11/25 12:10:44.227
   STEP: cleanup: deleting ServiceAccount install-quay-own-ns-sa-bx7w in namespace olmv1-quay-own-ns-ns-nmnv @ 08/11/25 12:10:44.228
   STEP: cleaning up namespace olmv1-quay-own-ns-ns-nmnv @ 08/11/25 12:10:44.228
 • [5.908 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 5.908 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
 Running Suite:  - /Users/camilam/go/src/github/operator-framework-operator-controller/openshift/tests-extension
 ===============================================================================================================
 Random Seed: 1754910630 - will randomize all specs

 Will run 1 of 1 specs
 ------------------------------
 [sig-olmv1] OLMv1 should pass a trivial sanity check
 /Users/camilam/go/src/github/operator-framework-operator-controller/openshift/tests-extension/test/olmv1.go:28
 • [0.000 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 0.001 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
 Running Suite:  - /Users/camilam/go/src/github/operator-framework-operator-controller/openshift/tests-extension
 ===============================================================================================================
 Random Seed: 1754910630 - will randomize all specs

 Will run 1 of 1 specs
 ------------------------------
 [sig-olmv1][OCPFeatureGate:NewOLM][Skipped:Disconnected] OLMv1 operator installation should fail to install a non-existing cluster extension
 /Users/camilam/go/src/github/operator-framework-operator-controller/openshift/tests-extension/test/olmv1.go:113
   STEP: creating namespace install-test-ns-42zt for single-namespace tests @ 08/11/25 12:10:44.5
   STEP: ensuring no ClusterExtension and CRD for non-existing operator @ 08/11/25 12:10:44.617
   STEP: deleting ClusterExtension install-test-ce-xgvx (package: does-not-exist) @ 08/11/25 12:10:44.75
   STEP: applying the ClusterExtension resource @ 08/11/25 12:10:47.116
   STEP: ensuring ServiceAccount is available before proceeding @ 08/11/25 12:10:47.237
   STEP: ensuring ClusterRoleBinding is available before proceeding @ 08/11/25 12:10:47.555
   STEP: waiting for the ClusterExtension to exist @ 08/11/25 12:10:47.862
   STEP: waiting up to 2 minutes for ClusterExtension to report failure @ 08/11/25 12:10:47.983
 • [4.287 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 4.288 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
 Running Suite:  - /Users/camilam/go/src/github/operator-framework-operator-controller/openshift/tests-extension
 ===============================================================================================================
 Random Seed: 1754910630 - will randomize all specs

 Will run 1 of 1 specs
 ------------------------------
 [sig-olmv1][OCPFeatureGate:NewOLM][Skipped:Disconnected] OLMv1 operator installation should block cluster upgrades if an incompatible operator is installed
 /Users/camilam/go/src/github/operator-framework-operator-controller/openshift/tests-extension/test/olmv1.go:147
   STEP: creating namespace install-test-ns-gqd4 for single-namespace tests @ 08/11/25 12:10:48.794
   STEP: ensuring no ClusterExtension no ClusterExtension and CRD for cluster-logging @ 08/11/25 12:10:48.913
   STEP: deleting ClusterExtension install-test-ce-j6v9 (package: cluster-logging) @ 08/11/25 12:10:49.042
   STEP: deleting ClusterExtension install-test-ce-jwss (package: cluster-logging) @ 08/11/25 12:10:51.41
   STEP: applying the ClusterExtension resource @ 08/11/25 12:10:51.789
   STEP: ensuring ServiceAccount is available before proceeding @ 08/11/25 12:10:51.914
   STEP: ensuring ClusterRoleBinding is available before proceeding @ 08/11/25 12:10:52.162
   STEP: waiting for the cluster-logging ClusterExtension to be installed @ 08/11/25 12:10:52.47
   STEP: ensuring the cluster is not upgradeable when olm.maxopenshiftversion is specified @ 08/11/25 12:10:55.946
 • [7.954 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 7.954 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
 Running Suite:  - /Users/camilam/go/src/github/operator-framework-operator-controller/openshift/tests-extension
 ===============================================================================================================
 Random Seed: 1754910630 - will randomize all specs

 Will run 1 of 1 specs
 ------------------------------
 [sig-olmv1][OCPFeatureGate:NewOLM][Skipped:Disconnected] OLMv1 operator installation should install a cluster extension
 /Users/camilam/go/src/github/operator-framework-operator-controller/openshift/tests-extension/test/olmv1.go:97
   STEP: creating namespace install-test-ns-trps for single-namespace tests @ 08/11/25 12:10:56.749
   STEP: ensuring no ClusterExtension and CRD for quay-operator @ 08/11/25 12:10:56.878
   STEP: deleting ClusterExtension install-quay-own-ns-ce-bx7w (package: quay-operator) @ 08/11/25 12:10:57.008
   STEP: applying the ClusterExtension resource @ 08/11/25 12:10:59.538
   STEP: ensuring ServiceAccount is available before proceeding @ 08/11/25 12:10:59.66
   STEP: ensuring ClusterRoleBinding is available before proceeding @ 08/11/25 12:10:59.901
   STEP: waiting for the quay-operator ClusterExtension to be installed @ 08/11/25 12:11:00.174
 • [6.599 seconds]
 ------------------------------

 Ran 1 of 1 Specs in 6.599 seconds
 SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 0 Skipped
[
 {
   "name": "[sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected][Serial] OLMv1 operator installation support for singleNamespace watch mode with quay-operator should install a cluster extension successfully",
   "lifecycle": "blocking",
   "duration": 3932,
   "startTime": "2025-08-11 11:10:31.234355 UTC",
   "endTime": "2025-08-11 11:10:35.166661 UTC",
   "result": "passed",
   "output": "  STEP: checking if OpenShift is available for tests @ 08/11/25 12:10:31.234\n  STEP: ensuring no ClusterExtension and CRD for quay-operator @ 08/11/25 12:10:31.235\n  STEP: creating namespace olmv1-quay-singlens-ns-dvnh for single-namespace tests @ 08/11/25 12:10:31.803\n  STEP: creating ServiceAccount @ 08/11/25 12:10:31.925\n  STEP: ensuring ServiceAccount is available before proceeding @ 08/11/25 12:10:32.049\n  STEP: registering cleanup for ServiceAccount @ 08/11/25 12:10:32.168\n  STEP: creating ClusterRoleBinding @ 08/11/25 12:10:32.168\n  STEP: ensuring ClusterRoleBinding is available before proceeding @ 08/11/25 12:10:32.289\n  STEP: registering cleanup for ClusterRoleBinding @ 08/11/25 12:10:32.411\n  STEP: creating ClusterExtension with the watch-namespace annotation @ 08/11/25 12:10:32.412\n  STEP: registering cleanup for ClusterExtension @ 08/11/25 12:10:32.572\n  STEP: waiting for the ClusterExtension to be installed @ 08/11/25 12:10:32.573\n  STEP: cleanup: deleting ClusterExtension install-quay-singlens-ce-x8gb @ 08/11/25 12:10:34.935\n  STEP: cleanup: deleting ClusterRoleBinding install-quay-singlens-crb-x8gb @ 08/11/25 12:10:34.936\n  STEP: cleanup: deleting ServiceAccount install-quay-singlens-sa-x8gb in namespace olmv1-quay-singlens-ns-dvnh @ 08/11/25 12:10:34.936\n  STEP: cleaning up namespace olmv1-quay-singlens-ns-dvnh @ 08/11/25 12:10:34.936\n"
 },
 {
   "name": "[sig-olmv1][OCPFeatureGate:NewOLM] OLMv1 CRDs should be installed",
   "lifecycle": "blocking",
   "duration": 4314,
   "startTime": "2025-08-11 11:10:31.234375 UTC",
   "endTime": "2025-08-11 11:10:35.548437 UTC",
   "result": "passed",
   "output": "  STEP: verifying CRD clusterextensions.olm.operatorframework.io @ 08/11/25 12:10:35.291\n  STEP: verifying CRD clustercatalogs.olm.operatorframework.io @ 08/11/25 12:10:35.421\n"
 },
 {
   "name": "[sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected][Serial] OLMv1 operator installation support for ownNamespace watch mode with an operator that does not support ownNamespace installation mode should fail to install a cluster extension successfully",
   "lifecycle": "blocking",
   "duration": 7237,
   "startTime": "2025-08-11 11:10:31.234383 UTC",
   "endTime": "2025-08-11 11:10:38.472294 UTC",
   "result": "passed",
   "output": "  STEP: checking if OpenShift is available for tests @ 08/11/25 12:10:35.549\n  STEP: ensuring no ClusterExtension and CRD for openshift-pipelines-operator-rh @ 08/11/25 12:10:35.549\n  STEP: deleting ClusterExtension install-pipelines-fail-own-ns-ce-d6v4 (package: openshift-pipelines-operator-rh) @ 08/11/25 12:10:35.681\n  STEP: creating namespace olmv1-pipelines-fail-own-ns-ns-p6gb for failing tests @ 08/11/25 12:10:36.044\n  STEP: creating ServiceAccount @ 08/11/25 12:10:36.167\n  STEP: ensuring ServiceAccount is available before proceeding @ 08/11/25 12:10:36.289\n  STEP: registering cleanup for ServiceAccount @ 08/11/25 12:10:36.41\n  STEP: creating ClusterRoleBinding @ 08/11/25 12:10:36.41\n  STEP: ensuring ClusterRoleBinding is available before proceeding @ 08/11/25 12:10:36.534\n  STEP: registering cleanup for ClusterRoleBinding @ 08/11/25 12:10:36.96\n  STEP: creating ClusterExtension with the watch-namespace annotation @ 08/11/25 12:10:36.961\n  STEP: registering cleanup for ClusterExtension @ 08/11/25 12:10:37.11\n  STEP: waiting for the ClusterExtension to fail installation @ 08/11/25 12:10:37.111\n  STEP: cleanup: deleting ClusterExtension install-pipelines-fail-own-ns-ce-h88d @ 08/11/25 12:10:38.345\n  STEP: cleanup: deleting ClusterRoleBinding install-pipelines-fail-own-ns-crb-h88d @ 08/11/25 12:10:38.346\n  STEP: cleanup: deleting ServiceAccount install-pipelines-fail-own-ns-sa-h88d in namespace olmv1-pipelines-fail-own-ns-ns-p6gb @ 08/11/25 12:10:38.346\n  STEP: cleaning up namespace olmv1-pipelines-fail-own-ns-ns-p6gb @ 08/11/25 12:10:38.346\n"
 },
 {
   "name": "[sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected][Serial] OLMv1 operator installation support for ownNamespace watch mode with quay-operator should install a cluster extension successfully",
   "lifecycle": "blocking",
   "duration": 13146,
   "startTime": "2025-08-11 11:10:31.234386 UTC",
   "endTime": "2025-08-11 11:10:44.381252 UTC",
   "result": "passed",
   "output": "  STEP: checking if OpenShift is available for tests @ 08/11/25 12:10:38.473\n  STEP: ensuring no ClusterExtension and CRD for quay-operator @ 08/11/25 12:10:38.473\n  STEP: deleting ClusterExtension install-quay-singlens-ce-x8gb (package: quay-operator) @ 08/11/25 12:10:38.648\n  STEP: creating namespace olmv1-quay-own-ns-ns-nmnv for own-namespace tests @ 08/11/25 12:10:41.138\n  STEP: creating ServiceAccount @ 08/11/25 12:10:41.26\n  STEP: ensuring ServiceAccount is available before proceeding @ 08/11/25 12:10:41.379\n  STEP: registering cleanup for ServiceAccount @ 08/11/25 12:10:41.497\n  STEP: creating ClusterRoleBinding @ 08/11/25 12:10:41.497\n  STEP: ensuring ClusterRoleBinding is available before proceeding @ 08/11/25 12:10:41.629\n  STEP: registering cleanup for ClusterRoleBinding @ 08/11/25 12:10:41.749\n  STEP: creating ClusterExtension with the watch-namespace annotation @ 08/11/25 12:10:41.749\n  STEP: registering cleanup for ClusterExtension @ 08/11/25 12:10:41.87\n  STEP: waiting for the ClusterExtension to be installed @ 08/11/25 12:10:41.871\n  STEP: cleanup: deleting ClusterExtension install-quay-own-ns-ce-bx7w @ 08/11/25 12:10:44.227\n  STEP: cleanup: deleting ClusterRoleBinding install-quay-own-ns-crb-bx7w @ 08/11/25 12:10:44.227\n  STEP: cleanup: deleting ServiceAccount install-quay-own-ns-sa-bx7w in namespace olmv1-quay-own-ns-ns-nmnv @ 08/11/25 12:10:44.228\n  STEP: cleaning up namespace olmv1-quay-own-ns-ns-nmnv @ 08/11/25 12:10:44.228\n"
 },
 {
   "name": "[sig-olmv1] OLMv1 should pass a trivial sanity check",
   "lifecycle": "blocking",
   "duration": 13148,
   "startTime": "2025-08-11 11:10:31.234386 UTC",
   "endTime": "2025-08-11 11:10:44.382407 UTC",
   "result": "passed",
   "output": ""
 },
 {
   "name": "[sig-olmv1][OCPFeatureGate:NewOLM][Skipped:Disconnected] OLMv1 operator installation should fail to install a non-existing cluster extension",
   "lifecycle": "blocking",
   "duration": 17436,
   "startTime": "2025-08-11 11:10:31.234387 UTC",
   "endTime": "2025-08-11 11:10:48.670504 UTC",
   "result": "passed",
   "output": "  STEP: creating namespace install-test-ns-42zt for single-namespace tests @ 08/11/25 12:10:44.5\n  STEP: ensuring no ClusterExtension and CRD for non-existing operator @ 08/11/25 12:10:44.617\n  STEP: deleting ClusterExtension install-test-ce-xgvx (package: does-not-exist) @ 08/11/25 12:10:44.75\n  STEP: applying the ClusterExtension resource @ 08/11/25 12:10:47.116\n  STEP: ensuring ServiceAccount is available before proceeding @ 08/11/25 12:10:47.237\n  STEP: ensuring ClusterRoleBinding is available before proceeding @ 08/11/25 12:10:47.555\n  STEP: waiting for the ClusterExtension to exist @ 08/11/25 12:10:47.862\n  STEP: waiting up to 2 minutes for ClusterExtension to report failure @ 08/11/25 12:10:47.983\n"
 },
 {
   "name": "[sig-olmv1][OCPFeatureGate:NewOLM][Skipped:Disconnected] OLMv1 operator installation should block cluster upgrades if an incompatible operator is installed",
   "lifecycle": "blocking",
   "duration": 25390,
   "startTime": "2025-08-11 11:10:31.234390 UTC",
   "endTime": "2025-08-11 11:10:56.625125 UTC",
   "result": "passed",
   "output": "  STEP: creating namespace install-test-ns-gqd4 for single-namespace tests @ 08/11/25 12:10:48.794\n  STEP: ensuring no ClusterExtension no ClusterExtension and CRD for cluster-logging @ 08/11/25 12:10:48.913\n  STEP: deleting ClusterExtension install-test-ce-j6v9 (package: cluster-logging) @ 08/11/25 12:10:49.042\n  STEP: deleting ClusterExtension install-test-ce-jwss (package: cluster-logging) @ 08/11/25 12:10:51.41\n  STEP: applying the ClusterExtension resource @ 08/11/25 12:10:51.789\n  STEP: ensuring ServiceAccount is available before proceeding @ 08/11/25 12:10:51.914\n  STEP: ensuring ClusterRoleBinding is available before proceeding @ 08/11/25 12:10:52.162\n  STEP: waiting for the cluster-logging ClusterExtension to be installed @ 08/11/25 12:10:52.47\n  STEP: ensuring the cluster is not upgradeable when olm.maxopenshiftversion is specified @ 08/11/25 12:10:55.946\n"
 },
 {
   "name": "[sig-olmv1][OCPFeatureGate:NewOLM][Skipped:Disconnected] OLMv1 operator installation should install a cluster extension",
   "lifecycle": "blocking",
   "duration": 31990,
   "startTime": "2025-08-11 11:10:31.234388 UTC",
   "endTime": "2025-08-11 11:11:03.224721 UTC",
   "result": "passed",
   "output": "  STEP: creating namespace install-test-ns-trps for single-namespace tests @ 08/11/25 12:10:56.749\n  STEP: ensuring no ClusterExtension and CRD for quay-operator @ 08/11/25 12:10:56.878\n  STEP: deleting ClusterExtension install-quay-own-ns-ce-bx7w (package: quay-operator) @ 08/11/25 12:10:57.008\n  STEP: applying the ClusterExtension resource @ 08/11/25 12:10:59.538\n  STEP: ensuring ServiceAccount is available before proceeding @ 08/11/25 12:10:59.66\n  STEP: ensuring ClusterRoleBinding is available before proceeding @ 08/11/25 12:10:59.901\n  STEP: waiting for the quay-operator ClusterExtension to be installed @ 08/11/25 12:11:00.174\n"
 }
]

Assisted-by: Gemini

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@camilamacedo86 camilamacedo86 force-pushed the single-add-ote branch 2 times, most recently from dec72bb to 3913bae Compare August 11, 2025 12:03
@camilamacedo86
Copy link
Contributor Author

/test e2e-aws-techpreview-olmv1-ext

@camilamacedo86
Copy link
Contributor Author

/test e2e-aws-techpreview-olmv1-ext

@camilamacedo86 camilamacedo86 changed the title OPRUN-4057: Migrate single/own namespace tests WIP: OPRUN-4057: Migrate single/own namespace tests Aug 12, 2025
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 12, 2025
@camilamacedo86
Copy link
Contributor Author

/retest-required

@camilamacedo86 camilamacedo86 force-pushed the single-add-ote branch 2 times, most recently from e87c877 to 7dbc583 Compare August 19, 2025 19:10
@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 20, 2025

@camilamacedo86: This pull request references OPRUN-4057 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set.

In response to this:

This commit migrates the OLMv1 single and own namespace watch mode tests from openshift/origin/test/extended/olm/olmv1-singleownnamespace.go to this repository. This is part of the effort to move component-specific tests into their respective downstream locations.

Tests

See that we need to name the tests to add [Serial]

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 20, 2025

@camilamacedo86: This pull request references OPRUN-4057 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set.

In response to this:

This commit migrates the OLMv1 single and own namespace watch mode tests from openshift/origin/test/extended/olm/olmv1-singleownnamespace.go to this repository. This is part of the effort to move component-specific tests into their respective downstream locations.

PS.: See that we need to name the tests to add [Serial]

Tests

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@camilamacedo86
Copy link
Contributor Author

/payload-aggregate periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-techpreview-serial 10

Copy link
Contributor

openshift-ci bot commented Aug 20, 2025

@camilamacedo86: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

  • periodic-ci-openshift-release-master-ci-4.20-e2e-gcp-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fa4a1a60-7dad-11f0-856b-9bcfe9c1c15c-0

@openshift-ci-robot
Copy link

openshift-ci-robot commented Aug 20, 2025

@camilamacedo86: This pull request references OPRUN-4057 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.20.0" version, but no target version was set.

In response to this:

This commit migrates the OLMv1 single and own namespace watch mode tests from openshift/origin/test/extended/olm/olmv1-singleownnamespace.go to this repository. This is part of the effort to move component-specific tests into their respective downstream locations.

PS.: See that we need to name the tests to add [Serial]

Tests

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fa4a1a60-7dad-11f0-856b-9bcfe9c1c15c-0

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@camilamacedo86 camilamacedo86 changed the title WIP: OPRUN-4057: Migrate single/own namespace tests OPRUN-4057: Migrate single/own namespace tests Aug 20, 2025
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 20, 2025
@camilamacedo86
Copy link
Contributor Author

camilamacedo86 commented Aug 20, 2025

@camilamacedo86
Copy link
Contributor Author

@camilamacedo86
Copy link
Contributor Author

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 20, 2025
This commit migrates the OLMv1 single and own namespace watch mode tests from openshift/origin/test/extended/olm/olmv1-singleownnamespace.go to this repository. This is part of the effort to move component-specific tests into their respective downstream locations.

Assisted-by: Gemini
Copy link
Contributor

openshift-ci bot commented Aug 21, 2025

@camilamacedo86: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/openshift-e2e-aws-techpreview 0174327 link false /test openshift-e2e-aws-techpreview

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@perdasilva
Copy link
Contributor

/approve

Copy link
Contributor

openshift-ci bot commented Aug 21, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: camilamacedo86, perdasilva

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 21, 2025
@camilamacedo86
Copy link
Contributor Author

@tmshort could you give a hand in this one?
Could we get it merged?

See that was tested with aggregate as well:
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/fa4a1a60-7dad-11f0-856b-9bcfe9c1c15c-0

Comment on lines +72 to +110
{
"name": "[sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected][Serial] OLMv1 operator installation support for singleNamespace watch mode with quay-operator should install a cluster extension successfully",
"originalName": "[sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected] OLMv1 operator installation support for singleNamespace watch mode with quay-operator should install a cluster extension successfully",
"labels": {
"original-name:[sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected] OLMv1 operator installation support for singleNamespace watch mode with quay-operator should install a cluster extension successfully": {}
},
"resources": {
"isolation": {}
},
"source": "openshift:payload:olmv1",
"lifecycle": "blocking",
"environmentSelector": {}
},
{
"name": "[sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected][Serial] OLMv1 operator installation support for ownNamespace watch mode with quay-operator should install a cluster extension successfully",
"originalName": "[sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected] OLMv1 operator installation support for ownNamespace watch mode with quay-operator should install a cluster extension successfully",
"labels": {
"original-name:[sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected] OLMv1 operator installation support for ownNamespace watch mode with quay-operator should install a cluster extension successfully": {}
},
"resources": {
"isolation": {}
},
"source": "openshift:payload:olmv1",
"lifecycle": "blocking",
"environmentSelector": {}
},
{
"name": "[sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected][Serial] OLMv1 operator installation support for ownNamespace watch mode with an operator that does not support ownNamespace installation mode should fail to install a cluster extension successfully",
"originalName": "[sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected] OLMv1 operator installation support for ownNamespace watch mode with an operator that does not support ownNamespace installation mode should fail to install a cluster extension successfully",
"labels": {
"original-name:[sig-olmv1][OCPFeatureGate:NewOLMOwnSingleNamespace][Skipped:Disconnected] OLMv1 operator installation support for ownNamespace watch mode with an operator that does not support ownNamespace installation mode should fail to install a cluster extension successfully": {}
},
"resources": {
"isolation": {}
},
"source": "openshift:payload:olmv1",
"lifecycle": "blocking",
"environmentSelector": {}
},
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So, you made these all Serial?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

They were serial but were missing the Serial in the name

@tmshort
Copy link
Contributor

tmshort commented Aug 21, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 21, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 0c4f430 and 2 for PR HEAD 0174327 in total

@openshift-merge-bot openshift-merge-bot bot merged commit 2ed1a5c into openshift:main Aug 22, 2025
12 of 13 checks passed
@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: ose-olm-operator-controller
This PR has been included in build ose-olm-operator-controller-container-v4.21.0-202508221047.p0.g2ed1a5c.assembly.stream.el9.
All builds following this will include this PR.

@camilamacedo86 camilamacedo86 deleted the single-add-ote branch August 22, 2025 13:34
@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: ose-olm-catalogd
This PR has been included in build ose-olm-catalogd-container-v4.21.0-202508221047.p0.g2ed1a5c.assembly.stream.el9.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants